Remove duplicate SpotBugs defaults #333
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
timja
approved these changes
Nov 2, 2022
NotMyFault
approved these changes
Nov 2, 2022
MarkEWaite
added a commit
to MarkEWaite/jenkins.io
that referenced
this pull request
Nov 4, 2022
The spotbugs excludes filter file is now enabled automatically if a file with the correct name is found. There is no longer any need to add the entry into the pom.xml file. See https://github.com/jenkinsci/pom/releases/tag/jenkins-1.91 and jenkinsci/pom#333
MarkEWaite
added a commit
to jenkins-infra/jenkins.io
that referenced
this pull request
Nov 4, 2022
The spotbugs excludes filter file is now enabled automatically if a file with the correct name is found. There is no longer any need to add the entry into the pom.xml file. See https://github.com/jenkinsci/pom/releases/tag/jenkins-1.91 and jenkinsci/pom#333
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The version of the SpotBugs Maven Plugin that we are using already defines the
failOnError,effort,threshold, andexcludeFilterFilemojo parameters to the values of thespotbugs.failOnError,spotbugs.threshold,spotbugs.effort, orspotbugs.excludeFilterFileproperties if set, with the same defaults as ours if these properties are not set (see https://github.com/spotbugs/spotbugs-maven-plugin/blob/f01a7f6b99da3d2e6dcdbddd20f0b4e4dfac73fa/src/main/groovy/org/codehaus/mojo/spotbugs/BaseViolationCheckMojo.groovy). As such it is completely redundant to declare these defaults ourselves and configure the mojo with them. To test this, I compiled the Swarm client with these changes and observed that thespotbugs.excludeFilterFileandspotbugs.thresholdsettings still took effect with the changes in this PR.